Skip to content

Rebuild for mkl 2025#60

Open
regro-cf-autotick-bot wants to merge 11 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-mkl2025-0-1_hcde6d2
Open

Rebuild for mkl 2025#60
regro-cf-autotick-bot wants to merge 11 commits intoconda-forge:mainfrom
regro-cf-autotick-bot:rebuild-mkl2025-0-1_hcde6d2

Conversation

@regro-cf-autotick-bot
Copy link
Contributor

@regro-cf-autotick-bot regro-cf-autotick-bot commented Dec 9, 2025

This PR has been triggered in an effort to update mkl2025.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/20051212824 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Dec 9, 2025 •
edited
Loading

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/22245390951. Examine the logs at this URL for more detail.

@h-vetinari
MNT: Re-rendered with conda-smithy 3.54.1 and conda-forge-pinning 202…
b316948 
…5.12.25.01.57.59

Other tools:
- conda-build 25.11.1
- rattler-build 0.54.0
- rattler-build-conda-compat 1.4.10
@h-vetinari
Copy link
Member

h-vetinari commented Dec 28, 2025

Test failures on osx

The following tests FAILED:
	  6 - 'Muscat.Bridges.CGNSBridge' (Failed)
	 95 - 'Muscat.IO.GReader' (Failed)
	108 - 'Muscat.IO.MeshFileConverter' (Failed)
	162 - 'Muscat.MeshContainers.PartitionedMesh' (Failed)

Looks like this is due to numpy 2.4 (as 2.3.5 ran fine a few weeks ago)

TypeError: Calling np.sum(generator) is deprecated.Use np.sum(np.fromiter(generator)) or the python sum builtin instead.

@h-vetinari h-vetinari force-pushed the rebuild-mkl2025-0-1_hcde6d2 branch from c6f0425 to fe8c0f1 Compare December 28, 2025 07:03
@h-vetinari
Copy link
Member

h-vetinari commented Dec 28, 2025

Requires conda-forge/eigency-feedstock#25

@h-vetinari h-vetinari mentioned this pull request Dec 28, 2025
Merged
10 tasks
@h-vetinari
Copy link
Member

h-vetinari commented Dec 29, 2025

Bunch of failures on windows along the lines of

ValueError: Buffer dtype mismatch, expected 'CMuscatIndex' but got 'long'

@fbordeu
Copy link
Contributor

fbordeu commented Dec 29, 2025

Hi, I'm away without access to a computer.

I think the inconsistencie comes from using a different version of numpy during compilation and running.

Can you tell me the used version of numpy? Numpy 2 in windows uses long int for indexing. I think we need to drop numpy 1 support and force numpy >= 2 during the build and run.

@h-vetinari
Copy link
Member

h-vetinari commented Jan 5, 2026

Can you tell me the used version of numpy?

I've updated this PR to compile against numpy 2; it needs to use numpy <2.4 because there's a deprecation that seems to get turned into an error...

h-vetinari
h-vetinari reviewed Feb 20, 2026
View reviewed changes
@Laureleen06
Copy link
Contributor

Laureleen06 commented Feb 20, 2026

I'm preparing a release for mid-March; I'll merge at that time.

@Laureleen06 Laureleen06 mentioned this pull request Feb 23, 2026
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@h-vetinari h-vetinari h-vetinari left review comments

@casenave casenave Awaiting requested review from casenave casenave is a code owner

@fbordeu fbordeu Awaiting requested review from fbordeu fbordeu is a code owner

@Laureleen06 Laureleen06 Awaiting requested review from Laureleen06 Laureleen06 is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@regro-cf-autotick-bot @conda-forge-admin @h-vetinari @fbordeu @Laureleen06